🗣 Description

Save what the result would have been for controls that are omitted if they had not been omitted to the JSON output (HTML output is unchanged). Two new keys are added for each test result:

• OmittedEvaluationResult: What the result would have been, e.g., "Fail"
• OmittedEvaluationDetails: What the report details string would have been, e.g., "1 agency domain(s) found in violation: example.com"

For tests that are not omitted, those keys will be set to "N/A". See screenshot below for an example.

💭 Motivation and context

Closes #1458.

🧪 Testing

• Add 12 new unit tests
• Ran ScubaGear with a control omitted, ensured that
  • The HTML output is unaffected by the new JSON keys
  • The OmittedEvaluationResult and OmittedEvaluationDetails values are correct for the omitted control.
  • The OmittedEvaluationResult and OmittedEvaluationDetails values are "N/A" for the controls that were not omitted.
• Compared the results with reports produced on main for two test tenants, verified that the results are consistent.

📷 Screenshots (if appropriate)

New keys indicated in red:

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• All future TODOs are captured in issues, which are referenced in code comments.
• These code changes follow the ScubaGear content style guide.
• Related issues these changes resolve are linked preferably via closing keywords.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.
• Unit tests added/updated to cover PowerShell and Rego changes.
• Functional tests added/updated to cover PowerShell and Rego changes.
• All relevant functional tests passed.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.

• Feature branch has been rebased against changes from parent branch, as needed

  Use Rebase branch button below or use this reference to rebase from the command line.

• Resolved all merge conflicts on branch

• Notified merge coordinator that PR is ready for merge via comment mention

• Demonstrate changes to the team for questions and comments.
  (Note: Only required for issues of size Medium or larger)

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.